home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Utilities Professional 1-1500
/
Utilities Professional 1-1500 (1994)(WPD)[!].iso
/
12511500
/
var1308.dms
/
var1308.adf
/
DNET2_10.LHA
/
DNet
/
Amiga
/
INSTALLATION
< prev
next >
Wrap
Text File
|
1989-12-11
|
5KB
|
147 lines
BASIC INSTALLATION AND RUN
--- AMIGA INSTALL ---
The 1.3 (or greater) serial.device must be used
The following must exist in L: and be mounted.
L:NULL-HANDLER
L:DPIPE-HANDLER (only required if you use the remote cli server)
The following must exist in S:
S:DNET.SERVERS
S:DNET.CONFIG
You may have to modify S:DNET.CONFIG to appropriately handle the
CONNECT message of your modem.
If you do not have a logical DNET: assignment where the server
executables are in DNET:AMIGA/BIN then you must modify S:DNET.SERVERS
to point to the appropriate server executables.
Make sure your path includes DNET:AMIGA/BIN or wherever you have placed
the client executables. This is required so DNET knows how to find
the FTERM executable when starting up the automatic FTERM.
--- UNIX INSTALL ---
You must set the enviroment variable DNETDIR in your .cshrc to an
initially empty directory (i.e. create an unobstrusive directory). This
directory will hold the UNIX domain sockets DNet uses to communicate.
Security on the UNIX side is solely determined by who has access to this
directory. For example:
Extract the distribution.
% cd dnet
% MAKE (you may have to chmod this +x, this is a shell script)
This compiles the code. Binaries should exist in dnet/unix/bin. If
you have problems not easily fixed please email me. Note that the
source only compiles on systems compatible with BSD 4.3 . The code
should compile on Suns running 3.5 but does not appear to run on
suns running 4.0 (??). The code compiles and runs on Dynix system
3.0.12 or higher. The code has been found to compile pretty well
on Sys V *with* berkeley socket extensions.
% cd ~
% mkdir .DNET
% vi .cshrc (and add the following line)
setenv DNETDIR ~/.DNET/
% source .cshrc (make sure the change is made part of your shell)
NOTE the trailing slash (/) on the DNETDIR enviroment variable. Do
not forget this.
Copy the UNIX dnet.servers file into ~/.DNET (or whatever directory
you had defined from DNETDIR.
******** RUN *******
Sequence of events (basic options, see dnet.doc for other options).
2400 baud is assumed in the below example, simply change where it
applies if running at a different baud rate.
(1) on amiga
(i) The connection to your system is 7 bits and parity is
ignored.
1> run dnet -b2400 -P0 -Z0
(ii) The connection to your system is 7 bits even parity and
parity is enforced.
1> run DNET -b2400 -P0 -Z2
(iii) The connection to your system is 8 bits and supports raw
8 bit transfers (no parity).
1> run DNET -b2400 -P0 -Z0 -m0
Other combinations may apply, see doc/dnet.doc for details. The
-P option selects the protocol and -Z selects parity.
(2) From small DNet window now open on the amiga.
Use the AT command set or otherwise instruct your modem to
dial your system. For hard connections where no modem exists
this is not necessary, though with some hard connections you
will need to use the SEND-BREAK menu option to send a line
break to get a system prompt.
Log into your UNIX account
(3) From the UNIX prompt: (be sure the DNETDIR enviroment variable
is set appropriately and your path contains the dnet executable
and clients.
(i) The connection to your system is 7 bits and parity is ignored,
% dnet
(ii) The connection to your system is 7 bits even parity and parity
is enforced
% stty -odd
% dnet
(iii) The connection to your system is 8 bits
% dnet -m0
(4) At this point the small dnet window should disappear. After a
few seconds an FTERM window should open and after another small
delay give you a shell prompt.
Congratulations, you are running DNet.
Now you may do all sorts of things. You may run other FTERM
windows from your amiga (1> run fterm) and therefore have
several shell windows... you can run file transfer clients
(putfiles and getfiles) on either the amiga or unix sides, etc...
read the documentation in the doc directory for more info.
SHUTTING DOWN
Logging out of an FTERM window does not kill DNet. To kill DNet
use the 'quitdnet' command on the Amiga side. This should kill all
connections and bring back the original small dnet window with the
original shell prompt from which you should be able to log out
normally. If you are unable to get the original shell prompt in
the small dnet window you may have to restart the protocol (menu
option) and try 'quitdnet' again. If all else fails simply hanging
up the modem should work (in which case you BREAK the dnet process
on the Amiga side).